-
Notifications
You must be signed in to change notification settings - Fork 1
Move OpenAI decorator to DFApp
class
#6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
# Conflicts: # azure/durable_functions/openai_agents/decorators.py # azure/durable_functions/openai_agents/model_invocation_activity.py
FunctionApp
classDFApp
class
|
||
return wrap | ||
|
||
def _create_invoke_model_activity(self, model_provider): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit concerned about bringing this much of OpenAI-related code directly into this file. Until now, all the code related to this integration was under the openai_agents folder, and I believe there is value in keeping it this way. Obviously, the entry point (durable_openai_agent_orchestrator) belongs to this class, but perhaps it can delegate to code remaining under openai_agents?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's fair, though I feel the app registration and "outer" activity/orchestration logic should live in this app type. I've moved the OpenAI-specific logic out.
Signed-off-by: Phillip Hoff <[email protected]>
Signed-off-by: Phillip Hoff <[email protected]>
Signed-off-by: Phillip Hoff <[email protected]>
Moves the
durable_openai_agent_orchestrator
decorator to theDFApp
class. This makes it easier for developers to find as well as eliminates logic needed to scan and find theFunctionApp
instance in the startup file.